home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat3n / netdir.z / netdir
Encoding:
Text File  |  2001-04-17  |  23.1 KB  |  256 lines

  1.  
  2.  
  3.  
  4. nnnneeeettttddddiiiirrrr((((3333NNNN))))                                                          nnnneeeettttddddiiiirrrr((((3333NNNN))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee, _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_aaaa_dddd_dddd_rrrr, _nnnn_eeee_tttt_dddd_iiii_rrrr______ffff_rrrr_eeee_eeee, _nnnn_eeee_tttt_dddd_iiii_rrrr______mmmm_eeee_rrrr_gggg_eeee_aaaa_dddd_dddd_rrrr,
  10.      _tttt_aaaa_dddd_dddd_rrrr_2222_uuuu_aaaa_dddd_dddd_rrrr, _uuuu_aaaa_dddd_dddd_rrrr_2222_tttt_aaaa_dddd_dddd_rrrr, _nnnn_eeee_tttt_dddd_iiii_rrrr______pppp_eeee_rrrr_rrrr_oooo_rrrr, _nnnn_eeee_tttt_dddd_iiii_rrrr______ssss_pppp_eeee_rrrr_rrrr_oooo_rrrr - generic
  11.      transport name-to-address translation
  12.  
  13. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  14.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_nnnn_eeee_tttt_dddd_iiii_rrrr_...._hhhh_>>>>
  15.      _iiii_nnnn_tttt _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee_((((_ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg _****_cccc_oooo_nnnn_ffff_iiii_gggg_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv
  16.          _****_ssss_eeee_rrrr_vvvv_iiii_cccc_eeee_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_dddd______aaaa_dddd_dddd_rrrr_llll_iiii_ssss_tttt _****_aaaa_dddd_dddd_rrrr_ssss_))))_;;;;
  17.      _iiii_nnnn_tttt _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_aaaa_dddd_dddd_rrrr_((((_ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg _****_cccc_oooo_nnnn_ffff_iiii_gggg_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt
  18.          _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv_llll_iiii_ssss_tttt _****_****_ssss_eeee_rrrr_vvvv_iiii_cccc_eeee_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _****_nnnn_eeee_tttt_aaaa_dddd_dddd_rrrr_))))_;;;;
  19.      _vvvv_oooo_iiii_dddd _nnnn_eeee_tttt_dddd_iiii_rrrr______ffff_rrrr_eeee_eeee_((((_vvvv_oooo_iiii_dddd _****_pppp_tttt_rrrr_,,,, _iiii_nnnn_tttt _iiii_dddd_eeee_nnnn_tttt_))))_;;;;
  20.      _iiii_nnnn_tttt _nnnn_eeee_tttt_dddd_iiii_rrrr______mmmm_eeee_rrrr_gggg_eeee_aaaa_dddd_dddd_rrrr_((((_ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg _****_cccc_oooo_nnnn_ffff_iiii_gggg_,,,, _cccc_hhhh_aaaa_rrrr _****_mmmm_rrrr_gggg______uuuu_aaaa_dddd_dddd_rrrr_,,,,
  21.          _cccc_hhhh_aaaa_rrrr _****_ssss______uuuu_aaaa_dddd_dddd_rrrr_,,,, _cccc_hhhh_aaaa_rrrr _****_cccc______uuuu_aaaa_dddd_dddd_rrrr_))))_;;;;
  22.      _cccc_hhhh_aaaa_rrrr _****_tttt_aaaa_dddd_dddd_rrrr_2222_uuuu_aaaa_dddd_dddd_rrrr_((((_ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg _****_cccc_oooo_nnnn_ffff_iiii_gggg_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _****_aaaa_dddd_dddd_rrrr_))))_;;;;
  23.      _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _****_uuuu_aaaa_dddd_dddd_rrrr_2222_tttt_aaaa_dddd_dddd_rrrr_((((_ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg _****_cccc_oooo_nnnn_ffff_iiii_gggg_,,,, _cccc_hhhh_aaaa_rrrr _****_uuuu_aaaa_dddd_dddd_rrrr_))))_;;;;
  24.      _iiii_nnnn_tttt _nnnn_eeee_tttt_dddd_iiii_rrrr______oooo_pppp_tttt_iiii_oooo_nnnn_ssss_((((_ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg _****_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_,,,, _iiii_nnnn_tttt _oooo_pppp_tttt_iiii_oooo_nnnn_,,,, _iiii_nnnn_tttt _ffff_dddd_,,,,
  25.          _cccc_hhhh_aaaa_rrrr _****_pppp_oooo_iiii_nnnn_tttt_eeee_rrrr______tttt_oooo______aaaa_rrrr_gggg_ssss_))))_;;;;
  26.      _vvvv_oooo_iiii_dddd _nnnn_eeee_tttt_dddd_iiii_rrrr______pppp_eeee_rrrr_rrrr_oooo_rrrr_((((_cccc_hhhh_aaaa_rrrr _****_ssss_))))_;;;;
  27.      _cccc_hhhh_aaaa_rrrr _****_nnnn_eeee_tttt_dddd_iiii_rrrr______ssss_pppp_eeee_rrrr_rrrr_oooo_rrrr_((((_vvvv_oooo_iiii_dddd_))))_;;;;
  28.  
  29. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  30.      These routines provide a generic interface for name-to-address mapping
  31.      that will work with a all transport protocols.  This interface provides a
  32.      generic way for programs to convert transport specific addresses into
  33.      common structures and back again.
  34.  
  35.      The _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee routine maps the machine name and service name in
  36.      the _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv structure to a collection of addresses of the type
  37.      understood by the transport identified in the _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg structure.  This
  38.      routine returns all addresses that are valid for that transport in the
  39.      _nnnn_dddd______aaaa_dddd_dddd_rrrr_llll_iiii_ssss_tttt structure.  The _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg structure is described on the
  40.      _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg(4) manual page.  The _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv and _nnnn_dddd______aaaa_dddd_dddd_rrrr_llll_iiii_ssss_tttt structures
  41.      have the following elements.
  42.           _nnnn_dddd______aaaa_dddd_dddd_rrrr_llll_iiii_ssss_tttt structure:
  43.                _iiii_nnnn_tttt            _nnnn______cccc_nnnn_tttt_;;;;       _////_**** _nnnn_uuuu_mmmm_bbbb_eeee_rrrr _oooo_ffff _nnnn_eeee_tttt_bbbb_uuuu_ffff_ssss _****_////
  44.                _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff  _****_nnnn______aaaa_dddd_dddd_rrrr_ssss_;;;;    _////_**** _tttt_hhhh_eeee _nnnn_eeee_tttt_bbbb_uuuu_ffff_ssss _****_////
  45.           _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv structure:
  46.                _cccc_hhhh_aaaa_rrrr _****_hhhh______hhhh_oooo_ssss_tttt_;;;;   _////_**** _tttt_hhhh_eeee _hhhh_oooo_ssss_tttt _nnnn_aaaa_mmmm_eeee _****_////
  47.                _cccc_hhhh_aaaa_rrrr _****_hhhh______ssss_eeee_rrrr_vvvv_;;;;   _////_**** _tttt_hhhh_eeee _ssss_eeee_rrrr_vvvv_iiii_cccc_eeee _nnnn_aaaa_mmmm_eeee _****_////
  48.  
  49.  
  50.  
  51.  
  52.  
  53.  
  54.  
  55.  
  56.                                                                         PPPPaaaaggggeeee 1111
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63. nnnneeeettttddddiiiirrrr((((3333NNNN))))                                                          nnnneeeettttddddiiiirrrr((((3333NNNN))))
  64.  
  65.  
  66.  
  67.      _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee accepts some special-case host names.  These host names
  68.      are hints to the underlying mapping routines that define the intent of
  69.      the request.  This information is required for some transport provider
  70.      developers to provide the correct information back to the caller.  The
  71.      host names are defined in _nnnn_eeee_tttt_dddd_iiii_rrrr_...._hhhh.  The currently defined host names
  72.      are:
  73.      _HHHH_OOOO_SSSS_TTTT______SSSS_EEEE_LLLL_FFFF   Represents the address to which local programs will bind
  74.                  their endpoints.  _HHHH_OOOO_SSSS_TTTT______SSSS_EEEE_LLLL_FFFF differs from the host name
  75.                  provided by _gggg_eeee_tttt_hhhh_oooo_ssss_tttt_nnnn_aaaa_mmmm_eeee(), which represents the address to
  76.                  which _r_e_m_o_t_e programs will bind their endpoints.
  77.  
  78.      _HHHH_OOOO_SSSS_TTTT______AAAA_NNNN_YYYY    Represents any host accessible by this transport provider.
  79.                  _HHHH_OOOO_SSSS_TTTT______AAAA_NNNN_YYYY allows applications to specify a required service
  80.                  without specifying a particular host name.
  81.  
  82.      _HHHH_OOOO_SSSS_TTTT______BBBB_RRRR_OOOO_AAAA_DDDD_CCCC_AAAA_SSSS_TTTT
  83.                  Represents the address for all hosts accessible by this
  84.                  transport provider.  Network requests to this address will be
  85.                  received by all machines.
  86.  
  87.      All fields of the _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv structure must be initialized.
  88.  
  89.      To find all available transports, call the _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee routine with
  90.      each _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg structure returned by the _gggg_eeee_tttt_nnnn_eeee_tttt_pppp_aaaa_tttt_hhhh call.
  91.  
  92.      The _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_aaaa_dddd_dddd_rrrr routine maps addresses to service names.  This
  93.      routine returns a list of host and service pairs that would yield this
  94.      address.  If more than one tuple of host and service name is returned
  95.      then the first tuple contains the preferred host and service names.  The
  96.      _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv_llll_iiii_ssss_tttt structure contains the following members:
  97.           _iiii_nnnn_tttt    _hhhh______cccc_nnnn_tttt_;;;;         _////_**** _tttt_hhhh_eeee _nnnn_uuuu_mmmm_bbbb_eeee_rrrr _oooo_ffff _nnnn_dddd______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv_ssss _****_////
  98.           _ssss_tttt_rrrr_uuuu_cccc_tttt _hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv  _****_hhhh______hhhh_oooo_ssss_tttt_ssss_eeee_rrrr_vvvv_ssss_;;;;  _////_**** _tttt_hhhh_eeee _eeee_nnnn_tttt_rrrr_iiii_eeee_ssss _****_////
  99.  
  100.      The _nnnn_eeee_tttt_dddd_iiii_rrrr______ffff_rrrr_eeee_eeee structure is used to free the structures allocated by the
  101.      name to address translation routines.
  102.  
  103.      The _nnnn_eeee_tttt_dddd_iiii_rrrr______mmmm_eeee_rrrr_gggg_eeee_aaaa_dddd_dddd_rrrr routine is used by a network service to return an
  104.      optimized network addresses to a client.  This routine takes the
  105.      universal address of the endpoint that the service has bound to, which is
  106.      pointed to by the _s__u_a_d_d_r parameter, and the address of the endpoint that
  107.      a request came in on, which is pointed to by the _c__u_a_d_d_r parameter, to
  108.      create an optimized address for communication with the service.  The
  109.      service address should be an address returned by the _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee
  110.      call, specified with the special host name _HHHH_OOOO_SSSS_TTTT______SSSS_EEEE_LLLL_FFFF.
  111.  
  112.      The _tttt_aaaa_dddd_dddd_rrrr_2222_uuuu_aaaa_dddd_dddd_rrrr and _uuuu_aaaa_dddd_dddd_rrrr_2222_tttt_aaaa_dddd_dddd_rrrr routines support translation between
  113.      universal addresses and TLI type netbufs.  They take and return character
  114.      string pointers.  The _tttt_aaaa_dddd_dddd_rrrr_2222_uuuu_aaaa_dddd_dddd_rrrr routine returns a pointer to a string
  115.      that contains the universal address and returns _NNNN_UUUU_LLLL_LLLL if the conversion is
  116.      not possible.  This is not a fatal condition as some transports may not
  117.      support a universal address form.
  118.  
  119.  
  120.                                                                         PPPPaaaaggggeeee 2222
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127. nnnneeeettttddddiiiirrrr((((3333NNNN))))                                                          nnnneeeettttddddiiiirrrr((((3333NNNN))))
  128.  
  129.  
  130.  
  131.      _o_p_t_i_o_n, _f_d, and _p_o_i_n_t_e_r__t_o__a_r_g_s are passed to the _nnnn_eeee_tttt_dddd_iiii_rrrr______oooo_pppp_tttt_iiii_oooo_nnnn_ssss routine
  132.      for the transport specified in _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_pppp.  There are four values for
  133.      _o_p_t_i_o_n:
  134.           _NNNN_DDDD______SSSS_EEEE_TTTT______BBBB_RRRR_OOOO_AAAA_DDDD_CCCC_AAAA_SSSS_TTTT
  135.           _NNNN_DDDD______SSSS_EEEE_TTTT______RRRR_EEEE_SSSS_EEEE_RRRR_VVVV_EEEE_DDDD_PPPP_OOOO_RRRR_TTTT
  136.           _NNNN_DDDD______CCCC_HHHH_EEEE_CCCC_KKKK______RRRR_EEEE_SSSS_EEEE_RRRR_VVVV_EEEE_DDDD_PPPP_OOOO_RRRR_TTTT
  137.           _NNNN_DDDD______MMMM_EEEE_RRRR_GGGG_EEEE_AAAA_DDDD_DDDD_RRRR
  138.      If a transport provider does not support an option, _nnnn_eeee_tttt_dddd_iiii_rrrr______oooo_pppp_tttt_iiii_oooo_nnnn_ssss
  139.      returns _----_1111 and sets ______nnnn_dddd_eeee_rrrr_rrrr_oooo_rrrr to _NNNN_DDDD______NNNN_OOOO_CCCC_TTTT_RRRR_LLLL.
  140.  
  141.      The specific actions of each option follow.
  142.  
  143.      _NNNN_DDDD______SSSS_EEEE_TTTT______BBBB_RRRR_OOOO_AAAA_DDDD_CCCC_AAAA_SSSS_TTTT    Sets the transport provider up to allow broadcast, if
  144.                          the transport supports broadcast.  _f_d is a file
  145.                          descriptor into the transport (that is, the result of
  146.                          a _tttt______oooo_pppp_eeee_nnnn of _////_dddd_eeee_vvvv_////_uuuu_dddd_pppp).  _p_o_i_n_t_e_r__t_o__a_r_g_s is not used.
  147.                          If this completes, broadcast operations may be
  148.                          performed on file descriptor _f_d.
  149.  
  150.      _NNNN_DDDD______SSSS_EEEE_TTTT______RRRR_EEEE_SSSS_EEEE_RRRR_VVVV_EEEE_DDDD_PPPP_OOOO_RRRR_TTTT Allows the application to bind to a reserved port, if
  151.                          that concept exists for the transport provider.  _f_d
  152.                          is a file descriptor into the transport (it must not
  153.                          be bound to an address).  If _p_o_i_n_t_e_r__t_o__a_r_g_s is _NNNN_UUUU_LLLL_LLLL,
  154.                          _f_d will be bound to a reserved port.  If
  155.                          _p_o_i_n_t_e_r__t_o__a_r_g_s is a pointer to a _nnnn_eeee_tttt_bbbb_uuuu_ffff structure,
  156.                          an attempt will be made to bind to a reserved port on
  157.                          the specified address.
  158.  
  159.      _NNNN_DDDD______CCCC_HHHH_EEEE_CCCC_KKKK______RRRR_EEEE_SSSS_EEEE_RRRR_VVVV_EEEE_DDDD_PPPP_OOOO_RRRR_TTTT
  160.                          Used to verify that an address corresponds to a
  161.                          reserved port, if that concept exists for the
  162.                          transport provider.  _f_d is not used.  _p_o_i_n_t_e_r__t_o__a_r_g_s
  163.                          is a pointer to a _nnnn_eeee_tttt_bbbb_uuuu_ffff structure that contains an
  164.                          address.  This option returns _0000 only if the address
  165.                          specified in _p_o_i_n_t_e_r__t_o__a_r_g_s is reserved.
  166.  
  167.      _NNNN_DDDD______MMMM_EEEE_RRRR_GGGG_EEEE_AAAA_DDDD_DDDD_RRRR        Used to take a ``local address'' (like the _0000_...._0000_...._0000_...._0000
  168.                          address that TCP uses) and return a ``real address''
  169.                          that client machines can connect to.  _f_d is not used.
  170.                          _p_o_i_n_t_e_r__t_o__a_r_g_s is a pointer to a _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_dddd______mmmm_eeee_rrrr_gggg_eeee_aaaa_rrrr_gggg,
  171.                          which has the following members:
  172.                            _cccc_hhhh_aaaa_rrrr _****_ssss______uuuu_aaaa_dddd_dddd_rrrr_;;;; _////_**** _ssss_eeee_rrrr_vvvv_eeee_rrrr_''''_ssss _uuuu_nnnn_iiii_vvvv_eeee_rrrr_ssss_aaaa_llll _aaaa_dddd_dddd_rrrr_eeee_ssss_ssss _****_////
  173.                            _cccc_hhhh_aaaa_rrrr _****_cccc______uuuu_aaaa_dddd_dddd_rrrr_;;;; _////_**** _cccc_llll_iiii_eeee_nnnn_tttt_''''_ssss _uuuu_nnnn_iiii_vvvv_eeee_rrrr_ssss_aaaa_llll _aaaa_dddd_dddd_rrrr_eeee_ssss_ssss _****_////
  174.                            _cccc_hhhh_aaaa_rrrr _****_mmmm______uuuu_aaaa_dddd_dddd_rrrr_;;;; _////_**** _mmmm_eeee_rrrr_gggg_eeee_dddd _uuuu_nnnn_iiii_vvvv_eeee_rrrr_ssss_aaaa_llll _aaaa_dddd_dddd_rrrr_eeee_ssss_ssss _****_////
  175.                          _ssss______uuuu_aaaa_dddd_dddd_rrrr is something like _0000_...._0000_...._0000_...._0000_...._1111_...._1111_2222, and, if the
  176.                          call is successful, _mmmm______uuuu_aaaa_dddd_dddd_rrrr will be set to something
  177.                          like _1111_9999_2222_...._1111_1111_...._1111_0000_9999_...._8888_9999_...._1111_...._1111_2222.  For most transports,
  178.                          _mmmm______uuuu_aaaa_dddd_dddd_rrrr is exactly what _ssss______uuuu_aaaa_dddd_dddd_rrrr is.
  179.  
  180.  
  181.  
  182.  
  183.  
  184.                                                                         PPPPaaaaggggeeee 3333
  185.  
  186.  
  187.  
  188.  
  189.  
  190.  
  191. nnnneeeettttddddiiiirrrr((((3333NNNN))))                                                          nnnneeeettttddddiiiirrrr((((3333NNNN))))
  192.  
  193.  
  194.  
  195.      The _nnnn_eeee_tttt_dddd_iiii_rrrr______pppp_eeee_rrrr_rrrr_oooo_rrrr() routine prints an error message on the standard
  196.      output stating why one of the name-to-address mapping routines failed.
  197.      The error message is preceded by the string given as an argument.
  198.  
  199.      The _nnnn_eeee_tttt_dddd_iiii_rrrr______ssss_pppp_eeee_rrrr_rrrr_oooo_rrrr routine returns a string containing an error message
  200.      stating why one of the name-to-address mapping routines failed.
  201.  
  202. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  203.      _gggg_eeee_tttt_nnnn_eeee_tttt_pppp_aaaa_tttt_hhhh(3N)
  204.  
  205.  
  206.  
  207.  
  208.  
  209.  
  210.  
  211.  
  212.  
  213.  
  214.  
  215.  
  216.  
  217.  
  218.  
  219.  
  220.  
  221.  
  222.  
  223.  
  224.  
  225.  
  226.  
  227.  
  228.  
  229.  
  230.  
  231.  
  232.  
  233.  
  234.  
  235.  
  236.  
  237.  
  238.  
  239.  
  240.  
  241.  
  242.  
  243.  
  244.  
  245.  
  246.  
  247.  
  248.  
  249.  
  250.                                                                         PPPPaaaaggggeeee 4444
  251.  
  252.  
  253.  
  254.